Enabling Calls to Emergency Numbers
The documentation here shows how to enable users to make emergency calls to emergency numbers (E911) from Skype for Business IP phones. It'll help you get started with configuring the infrastructure elements and call routing needed for making dynamic emergency calls.
|
●
|
'Dynamic' means the Teams client gets the emergency address/location based on the network location it is at and transmits it directly to the Public Safety Answering Point (PSAP), bypassing the Emergency Call Relay Center (ECRC). |
|
●
|
Based on the network topology that the tenant administrator defines, the Teams client provides network connectivity information in a request to the Teams Location Information Service (LIS). If there's a match, the Teams LIS returns a location to the client. This location data is transmitted back to the client. See here for more on configuring dynamic emergency calling. |
|
●
|
'Infrastructure elements' refers to information about the physical address of the building in which the devices are located and the network elements and their locations within it. |
|
➢
|
To configure emergency locations in Microsoft Teams admin center: |
|
1.
|
In the Microsoft Teams admin center, open the 'Emergency addresses' page. |
|
2.
|
Add addresses using the preceding and next figure as reference. |
|
3.
|
Click Save and then open the 'Networks & locations' page.
|
|
4.
|
Assign an emergency address to the network site using the preceding figure as reference. |
After configuring the emergency locations in the Microsoft Teams admin center, you can import them into Device Manager.
|
➢
|
To import emergency locations into Device Manager: |
|
1.
|
After configuring emergency locations in Microsoft Teams admin center, open the Emergency Locations page in Device Manager (Setup > System > Emergency Locations). |
|
2.
|
Click the Import button; a script exports the emergency locations from the Microsoft Teams admin center into OVOC from where they're imported into Device Manager. |
|
3.
|
Navigate to the folder in which the CSV file is saved. |
After the CSV file is imported, the locations are displayed in Device Manager's Emergency Locations table. Device Manager adds the values from the CSV without any manipulation except for removing leading / trailing white spaces.
|
4.
|
View the following columns in the newly created Emergency Locations table: |
|
●
|
Company Name - the name of the company in which the devices are deployed |
|
●
|
Description - a description of the company in which the devices are deployed |
|
●
|
Country - the name of the country in which the company is located |
|
●
|
State - the name of the state in which the company is located |
|
●
|
City - the name of the city in which the company is located |
|
●
|
Street - the name of the street in which the company is located |
|
●
|
Number - the street number of the company |
|
●
|
Postal Code - the postal code of the company |
|
●
|
Location - the company's department in which the devices are deployed |
|
●
|
ELIN - Emergency Location Identification Number. A 10-digit DID number that can be obtained from the local exchange carrier (LEC). Provide it to the public safety answering point (PSAP) for 911 calls. |
|
●
|
IP address - the device's IP address in the network |
|
●
|
Subnet - the subnet in which the device is deployed |
|
●
|
LLDP Switch - Link Layer Discovery Protocol switch. Devices use this link layer protocol to advertize their identity, capabilities and neighbors in a LAN based on IEEE 802. |
|
●
|
LLDP port - Link Layer Discovery Protocol port. |
Make sure two rows (or more) in the Emergency Locations table do not contain same combination of:
|
●
|
LLDP Switch Chassis number + LLDP port |
|
●
|
LLDP Switch Chassis number + EMPTY LLDP port |
|
5.
|
After importing the CSV file, edit the configuration template in the Configuration Template page (Setup > Configuration > Templates). |
|
6.
|
Configure the following (refer to the preceding figure): |
|
●
|
Set the parameter 'Configuration Key' to dm/report_status/paths |
|
●
|
Set the parameter 'Configuration Value' to |
dm/report_status/paths=status/network/lan/*,
status/diagnostics/lldp/chassis/chassisId,
status/diagnostics/lldp/chassis/portId
|
●
|
Configuration of these two parameters is mandatory for the feature to function. |
|
●
|
The configuration can be performed at either the device level, Tenant level, Group level or Site level. |